feat: add lighthouse test to CI #487
Open
+1,780
−17
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 tasks
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds automated Lighthouse CI performance testing to the workflow and implements a performance optimization for the orchestrator list rendering. The optimization defers rendering of the OrchestratorList component using requestAnimationFrame to allow the browser to paint the initial page layout first.
Changes:
- Added Lighthouse CI workflow that waits for Vercel preview deployments and runs performance tests
- Configured Lighthouse with desktop preset and performance thresholds for key metrics
- Implemented deferred rendering for OrchestratorList on home and orchestrators pages using requestAnimationFrame
Reviewed changes
Copilot reviewed 5 out of 6 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/lighthouse-vercel-preview.yml | New workflow that polls for Vercel preview deployment and runs Lighthouse CI tests |
| .lighthouserc.json | Lighthouse configuration with performance assertions for LCP, CLS, TBT, and overall score |
| package.json | Added @lhci/cli and wait-on as dev dependencies |
| pnpm-lock.yaml | Lock file updates for new dependencies and their transitive dependencies |
| pages/orchestrators.tsx | Added requestAnimationFrame-based deferred rendering of OrchestratorList |
| pages/index.tsx | Added requestAnimationFrame-based deferred rendering of OrchestratorList |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This was referenced Jan 14, 2026
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces automated Lighthouse performance checks to the CI workflow. It adds a dedicated Lighthouse job that runs on pull requests targeting the
mainbranch, sets up the required configuration for Lighthouse CI, and updates dependencies to support these checks.Pages that it checks:
/orchestratorsleaderboardtransactionsvotingtreasurySpeed Improvements
OrchestorsListnow renders only after the UI layout is painted, making the home and orchestrators page much faster when there is no cache availableCI/CD Pipeline Enhancements:
lighthousejob to.github/workflows/ci.ymlthat installs dependencies, builds the project, starts the server, waits for it to be ready, and then runs Lighthouse CI for PRs targetingmain.Performance Testing Configuration:
.lighthouserc.jsonwith Lighthouse CI settings, including test URLs, run count, desktop emulation, and performance assertions for key metrics like performance score, LCP, CLS, and TBT.Dependency Updates:
@lhci/clias a dev dependency inpackage.jsonto enable running Lighthouse CI in the workflow.wait-onas a dev dependency inpackage.jsonto allow the workflow to wait for the server to be ready before running Lighthouse.